fix(examples/ag-ui): pin published threadplane-middleware in deploy requirements#671
Merged
Conversation
…equirements #665 renamed threadplane-client-tools -> threadplane-middleware (editable [tool.uv.sources] path) but never regenerated requirements.txt, so the ag-ui-demo Railway image installed the old package and crashed on startup (ModuleNotFoundError: threadplane.middleware -> healthcheck fail -> stale container). threadplane-middleware 0.0.1 is now on PyPI; regenerate with --no-sources so the deploy pins the published package instead of the Docker-stripped editable path. Unblocks the demo backend (and F5 on the demo). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
ag-ui-demoRailway backend (ag-ui.threadplane.ai) has been deploy-broken since #665: that PR renamedthreadplane-client-tools→threadplane-middleware(updating the import + an editable[tool.uv.sources]path) but never regeneratedexamples/ag-ui/python/requirements.txt, which still pinnedthreadplane-client-tools==0.0.1. The Railway image installs fromrequirements.txtvia PyPI (it strips editable/file://lines), so the new container importedthreadplane.middleware(absent from the old package) and crashed on startup → healthcheck failed → Railway kept the stale container. Diagnosed via the Railway API (deploymentFAILED,ModuleNotFoundError: No module named 'threadplane.middleware').Fix
threadplane-middleware 0.0.1is now published to PyPI. Regeneratedrequirements.txtwithuv export --no-hashes **--no-sources**so the deploy pins the published package (threadplane-middleware==0.0.1) instead of emitting the editable-e ../../../packages/...line the Dockerfile strips. The--no-sourcesflag is now baked into the file's documented regen command so it can't re-drift; local dev still uses the editable path (sources override untouched in pyproject).Merging triggers
ag-ui-demo-deploy→ the new image installs the package → healthcheck passes → F5 subagent cards go live on the demo.🤖 Generated with Claude Code